System and method for wireless irrigation control with a remote application

ABSTRACT

Provided are a system and method for wireless irrigation control with a remote application. According to one embodiment, the system includes a processor and a plurality of interactive zone switches for connection to at least one irrigation device, each zone switch further structured and arranged to detect a state of the at least one irrigation device. A non-volatile memory is coupled to the processor and provided with processor executable instructions to direct operation of each interactive zone switch. There is at least one remote application to establish a schedule within the non-volatile memory for operation for each interactive zone switch and to receive the schedule from the non-volatile memory in response to a users desire to review or modify the schedule. A wireless network component is coupled to the processor and the non-volatile memory and is in communication with the at least one remote application to schedule operation of at least one interactive zone switch and the at least one irrigation device.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 13/302,987 filed Nov. 22, 2011, now U.S. Pat. No. ______. This continuing application claims the benefit of U.S. patent application Ser. No. 13/302,987.

FIELD OF THE INVENTION

The present invention relates generally to the field of automated irrigation systems and methods for their control and more specifically to automated irrigation systems controlled over existing wireless networks in connection with remote applications

BACKGROUND

Many homes enjoy private landscaping. Lawns, trees, shrubs and plants of many varieties can be used by homeowners or landscapers to create a pleasing personal outdoor environment. But plants, even of the desert variety, do require water to survive.

Many homes therefore are equipped with irrigation control systems in an effort to help the homeowner or landscape caregiver maintain the landscape plants. In their simplest form, a controller can be a set of valves that are manually activated when watering is desired. Manual operation is far from convenient in most settings so such control systems are not highly desired.

Often control systems are equipped with a timer so that valve operation can be established both for a given time of day and for a given duration. Establishing this watering schedule may be a tedious task involving tiny switches, codes and sequences of button presses upon a keypad. Entering a wrong button press or sequence can result in an undesired watering schedule that may or may not be immediately evident to the programmer. If not discovered, such errant programming may result in far too much water being provided, potentially resulting in not only water waste, but also overwatering if not flooding and damage land and structures. Too little water may result in plant death.

Adjustments to such watering systems are not easily made, so once a schedule is established many homeowners file the instruction manual away and never opt to change the schedule. As weather patterns change and perhaps even plants are replaced, grow or are removed, the failure to adjust the watering schedule may well result in waste of water resources as well less then desired care for the plants. Moreover the established watering schedule is maintained throughout the year, regardless of rain or heat.

Other shortcomings abound as well. Typical irrigation control systems operate in a linear fashion, which is to say that they operate a first zone for one duration, then move to activate a second zone for another duration, and then a third zone for yet another duration. Skipping a zone or watering zones out of order on different days may not be possible, and even if possible may not be easily achieved if the owner has misplaced his or her operating manual.

Further, some plants such as young plants, fresh grass and seeds for example often require frequent watering in short durations. Typical watering systems operating in a linear zone by zone fashion may not permit multiple repeated watering schedules.

Should a zone malfunction such systems do not inform the homeowner in any way, such that the first indication of a problem is typically the owner's observation of either flooding or dead dry plants.

Providing larger display panels on irrigation control systems may well help the owner/operator in programming and control, but such larger displays also increase costs. Also, as most irrigation control systems are placed in garages or closets, regardless of the display size and quality, actually viewing the display easily and in a comfortable environment may not be easy for all homeowners and operators.

Some watering systems have attempted to address some of these issues, such as for example U.S. Pat. No. 7,010,396 to Ware et al., entitled Irrigation Controller With Embedded Web Server, U.S. Pat. No. 6,832,239 to Sieminski entitled Internet-Enabled Central Irrigation Control, and US Patent Application 2009/0281672 to Pourzia entitled Weather Responsive Irrigation Systems and Methods.

In Ware, U.S. Pat. No. 7,010,396, an irrigation controller with an embedded web server activates irrigation devices in accordance with an event schedule. More specifically, “the controller 330 also contains an embedded web server that serves one or more web pages (not shown) to the browser equipped client(s) 320.” (Col. 6 lines 31-35).

Although perhaps beneficial in some settings, this web-serving ability of the Ware irrigation controller raises the complexity of the irrigation controller both in terms of it's fabrication process as well as it's method of use. Updates to features or corrections of software bugs must be made directly to the controller, which of course requires that the controller be on-line and in direct connection with the Internet. For users who do not wish to avail themselves of the Internet, Ware is impractical.

In Sieminski, U.S. Pat. No. 6,832,239, an irrigation controller is coupled to a wide area network, such as the Internet. More specifically, Sieminski teaches that a user does not communicate with the Sieminski irrigation control except through the Internet or via a stand alone controller, shown in Sieminski FIG. 2, which as illustrated and described appears typical of the existing display and button systems of conventional irrigation controllers.

As taught by Sieminski, the user establishes the schedule for watering with a web bases server that then transmits the schedule back through the Internet to a wireless carrier 108 which in turn is in communication with a plurality of wireless irrigation controllers 110.

Moreover, Sieminski is most applicable to a commercial setting where watering stations can be far apart such that wireless communication between the irrigation controller and the watering station is desirable. Centralization of the watering schedule with an Internet connected database may be beneficial in some settings, but if Internet access is not available or desired, the watering schedule cannot be accessed and implemented. Indeed a user of Sieminski must have not only a computer system, but also Internet access even if he or she is directly proximate to the watering area and controller if the web-based interface is to be used instead of the traditional on-device display and button system.

In Pourzia, US Patent Application 2009/0281672, the emphasis is for a weather responsive system that is truly composed of two key elements—the irrigation controller itself and it's access point. As is shown and described by Pourzia with respect to at least FIGS. 1 and 2, a user communicates with the controller 12 by way of a wireless access point 16 that is either coupled to the users computer (FIG. 1) or to a router (FIG. 2), with this second option being preferred so that the controller 12 can receive new instructions based on weather monitoring systems.

Moreover, all control is accomplished through the additional access point that is specific to the Pourzia system—not a pre-existing wireless access point such as may be found in many homes already. Further, all control is via web-browser interaction, with the irrigation controller having a dedicated and specific user interface system 56 which is again comprised of a typical output device such as a liquid crystal display and an input device such as a keypad as with many conventional irrigation controllers.

In addition, the master schedule is held by the client application and not the controller. This client application can be deployed to the user's computer or to the access point. Of course, if it is maintained by the user's computer, then no other systems can modify the system unless they are permitted access to the user's computer, which also must be on. This appears to present a potential problem. A user might well update the watering schedule via his or her personal computer and then shut the computer off. Later, an ASP server may attempt to update the schedule in response to developments overnight, such as for example morning rain, that the user was not aware of. However, as the master schedule is held by the browser application and not the controller, the adjustments attempted by the Internet based ASP server will not be reflected in the users master schedule, if it is even implemented as the client application was accessible. Pourzia does also teach that the access point can host the client application—which in turn would require greater complexity of the access point.

Moreover, many attempts have been made in repeated efforts to provide improved irrigation control in a simple and easily adjustable fashion. Although certainly necessary for the maintenance of plants, most homeowners and or other users do not see the watering system as being a priority and therefore are unlikely to embrace expensive systems that may also have multiple specialized components and or requirements.

Hence there is a need for a system and method that is capable of overcoming the above identified challenges.

SUMMARY

Embodiments of this invention provide a system and method for irrigation control, and more specifically to systems and methods for irrigation control by way of existing wireless home networks and remote configuration applications.

In particular, and by way of example only, according to one embodiment of the present invention, provided is a system for wireless irrigation control with remote application, including: a processor; a plurality of interactive zone switches for connection to at least one irrigation device, each zone switch further structured and arranged to detect a state of the at least one irrigation device; a non-volatile memory coupled to the processor having processor executable instructions to direct operation of each interactive zone switch; at least one remote application to establish a schedule within the non-volatile memory for operation for each interactive zone switch and to receive the schedule from the non-volatile memory in response to a users desire to review or modify the schedule; and a wireless network component coupled to the processor and the non-volatile memory and in communication with the at least one remote application to schedule operation of at least one interactive zone switch and the at least one irrigation device.

In yet another embodiment, provided is a method for wireless irrigation control with remote application, including: providing a plurality of interactive zone switches for connection to at least one irrigation device, each zone switch further structured and arranged to detect a state of the at least one irrigation device; providing a non-volatile memory coupled to a processor, the memory having processor executable instructions to direct the operation of each interactive zone switch; providing a wireless network component coupled to the processor and the non-volatile memory; providing at least one remote application to establish via the wireless network component a schedule within the non-volatile memory for operation of each interactive zone switch; and in response to a users desire to review or modify the schedule, retrieving the schedule from the non-volatile memory.

Further, in yet another embodiment, provided is a system for wireless irrigation control with remote application, including: a remote scheduler structured and arranged to provide a scheduling interface upon a display, the scheduling interface permitting a user to establish a schedule for at least one interactive zone switch coupled to at least one irrigation device; at least one irrigation controller, comprising: a processor; a plurality of interactive zone switches for connection to at least one irrigation device, each zone switch further structured and arranged to detect a state of the at least one irrigation device; a non-volatile memory coupled to the processor having processor executable instructions to direct operation of each interactive zone switch; and a wireless network component coupled to the processor and the non-volatile memory and in communication with the remote scheduler to exchange the schedule of at least one interactive zone switch and the at least one irrigation device, the schedule within the non-volatile memory being a master schedule.

BRIEF DESCRIPTION OF THE DRAWINGS

At least one method and system for irrigation control will be described, by way of example in the detailed description below with particular reference to the accompanying drawings in which like numerals refer to like elements, and:

FIG. 1 illustrates a level block diagram of an irrigation control system in accordance with at least one embodiment of the present invention;

FIG. 2 is a further refined block diagram of the controller and remote application for an irrigation control system in accordance with at least one embodiment of the present invention;

FIG. 3 is a conceptual circuit diagram of the controller for an irrigation control system in accordance with at least one embodiment of the present invention;

FIG. 4 is a flow diagram for a method of irrigation control in accordance with at least one embodiment of the present invention; and

FIG. 5 is a block diagram of at least one computer system in accordance with certain embodiments of the present invention.

DETAILED DESCRIPTION

Before proceeding with the detailed description, it is to be appreciated that the present teaching is by way of example only, not by limitation. The concepts herein are not limited to use or application with a specific system or method for irrigation control. Thus although the instrumentalities described herein are for the convenience of explanation shown and described with respect to exemplary embodiments, it will be understood and appreciated that the principles herein may be applied equally in other types of systems and methods for irrigation control.

Turning now to the figures, and more specifically to FIG. 1, illustrated is a high level block diagram of a wireless irrigation controlling system (“WICS”) 100 in accordance with at least one embodiment. As is further described in detail below, stated generally for at least one embodiment, the WICS 100 is structured and arranged to advantageous scheduling and control for a watering system by way of existing wireless networks and resources.

Moreover, the WICS 100 is entirely operable within the confines of a home network 102 or even an ad-hoc network, without need or requirement for Internet 104 resources. As is further discussed below, for some embodiments the Internet 104 may provide further access and control options, but it is not a requirement for each and every instance of use.

As conceptually illustrated within the home network 102, there are one or more computer systems 106 and an existing wireless network 108, such as but not limited to the 802.11 family of network standards, e.g. at the time of this writing 802.11 a/b/g/n. As shown the wireless access is provided by an existing device such as a wireless router 110 that may also be proving the home network 102 with access to the Internet 104. The home network 102 may also include one or more hand held computer devices 112, such as smart phones or tablet computes.

Home network 102 may also be an ad-hoc network 114, as in a decentralized wireless network that does not rely on preexisting infrastructure such as routers or access points. Rather each device or node participating in the ad-hoc network forwards data for other notes when and as necessary. For example, in at least one embodiment the home network 102 is, or may also include Bluetooth wireless connectivity.

As is shown, WICS 100 includes a controller 116 having a plurality of interactive switches for connection to at least one irrigation device 118, of which irrigation devices 118A, 118B and 118C are exemplary. WICS 100 further includes at least one remote application 120 to establish an irrigation schedule within the controller 116. More specifically, it is understood and appreciated that the controller 116 does not provide a direct interface for establishing or modifying the irrigation schedule. Further, the controller 116 does not provide active web-pages or a web-server for establishing or modifying the irrigation schedule. Moreover, the remote application 120 as is further described below is responsible for establishing or modifying the irrigation schedule.

The remote application 120 permits user operating a computer 106 or a hand held computer device 112, such as a smart phone or tablet computer to establish an irrigation schedule for the controller 116. Communication with the controller 116 is achieved by way of an existing wireless network. As shown for the home network 102 this may be a traditional wireless network 108 or an ad-hoc network 114. In addition, it should also be appreciated that where a user has only a hand held computing device 112 such as a smart phone or tablet computer, the user may obtain the application 120 from a remote server 122 coupled to the Internet 104.

With respect to FIG. 1, it is also appreciated that the home network 102 with controller 114 is shown as associated to a house 124. Exemplary houses 126 and 128 may also have similar home networks and their own installations of WICS 100.

It should be further appreciated, that because the WICS 100 is established as an element within home network 102, where such a home network 102 does provide access to the Internet, configuration and scheduling of the controller 116 may be accomplished by potentially any user having proper permission rights and computing resources who is also connected to the Internet 40.

Moreover, a gardener or landscaping service tending to house 124 and 126 may have access to computer 130 having an instance of the application 120. As computer 130 is coupled to the Internet 40, this user may be provided with access to monitor and adjust both installations of WICS 100 for houses 124 and 126.

FIG. 2 illustrates the home network 102 in enlarged form to more fully appreciate the elements of the controller 116 and the remote application 120 as they cooperatively provide WICS 100. For at least one embodiment, the controller 116 is shown to have a plurality of interactive zone switches 200, of which zone switches 200A, 200B, 200C and 200D are exemplary. As is described below, each zone switch 200 is further structured and arranged to detect a state of the irrigation device to which it is connected.

The controller 116 also has a processor 202 and a non-volatile memory 204 coupled to the processor 202, the non-volatile memory 204 having executable instructions to direct the operation of each interactive zone switch 200, in accordance with a master schedule 206 maintained by the non-volatile memory 204. A wireless network component 208 is also coupled to the processor and the non-volatile memory 204.

By way of an existing wireless network, such as an 802.11 network, or an ad-hoc network, such as but not limited to a Bluetooth connection, the wireless network component 208 permits the controller 116 to be in communication with at least one instance of the remote application 120 to establish a master schedule 206 for at least one interactive zone switch 200 and the irrigation device 118 to which it is connected.

With respect to the conceptual illustration of the controller 116 in FIG. 2, it is to be specifically noted that the controller 116 does not provide a web server or a local user interface such as a display and keypad. Moreover, to provide advantageous flexibility of features and ability with reduced production cost, at least one embodiment of controller 116 does not permit direct manual programming, requiring the operating user to use the remote application to establish a master schedule 206 within the non-volatile memory 204 for operation of each interactive zone switch 200.

Controller 116 may have a status light 210 that is operable to indicate the general status of the controller 116. For example the status light 210 may glow to indicate a general state of ON. For varying embodiments the status light 210 may also glow in different colors or blink to indicate various states, such as but not limited to—green as general status ok, blinking to indicate exchange of data with remote application 120, and or red to indicate a fault. In yet another embodiment each zone is represented by an indicator light such as an LED. Further, the LEDs may be configured to provide an indication of status, e.g. green for on, red for fault, and off for off. Further still, in at least one embodiment, WICS 100 is configured with a master switch operable to shut off all water supply, the master switch also having an LED stats light.

For at least one embodiment, the interactive zone switches 200, processor 202, non-volatile memory 204 and wireless network component 208 are disposed at least partially within a protective case 212, such as but not limited to a polycarbonate case. Further, although for ease of illustration the antenna 214 of wireless network component 208 is shown extending from the controller 116, the antenna 214 may be disposed within the case 212.

Controller 116 may also have an optional button 216 which when pressed sets the controller 116 into a state intended to help achieve initial wireless connection. For example, in at least one embodiment, depressing this button permits controller 116 to accept new Bluetooth paring, e.g. connections, for 60 seconds. If a connection is not established the controller 116 returns to the prior state. If a new connection is established, the remote application 120 permits configuration of the controller 116 for traditional wireless connection as well as Bluetooth connection. Companies, such as for example Netgear, offer similar push to connect options that may also be employed in varying embodiments.

As noted, each zone switch 200 is intended for connection to at least one irrigation device 118, of which irrigation devices 118A, 118B and 118C are exemplary. Each zone switch 200 is further structured and arranged to detect a state of the irrigation device to which it is connected. More specifically, in general the irrigation device is at least in part a solenoid activated valve, which when activated by the application of a current, permits water 218 to flow through the valve and irrigate the activated zone. Deactivation of the current allows the solenoid to close, and ceases the flow of water 218.

For at least one embodiment each zone switch 200 is structured and arranged to detect the state of the irrigation device by monitoring the current flow through the switch. For example, as shown zone switches 200A and 200B can detect that the irrigation devices 118A and 118B are operating as current is flowing to indicate that the solenoids of irrigation device 118A and 118B are operating. Zone switch 200D can detect that irrigation device 118D is not operating as a proper current flow is not detected indicating that the solenoid of irrigation device 118C has failed. Moreover, in varying embodiments the state of the irrigation device may be selected from the group consisting of connected, disconnected, open and closed. Each of these states may be compared to a record indicating the expected state to determine not only that the state is correct, but also the proper functioning of the irrigation device 118.

In addition, for at least one embodiment, WICS 100 may also be coupled to a water flow sensor 132 so as to sense the state of flow and confirm operation of a valve as intended and/or sense a leak in the system. The flow sensor 132 may further permit identification of a problem, such as where a drip line has been cut and the rate of flow detected by the flow sensor is greater than what a drip line would deliver. Of course, upon the detection of a fault with a valve based on sensed current or the detection of unintended or excessive water flow as provided by water flow sensor 132, for at least one embodiment, WICS is configured to send an alert which is registered by the application 120, i.e., a push message.

With respect to FIG. 2 a conceptual illustration of the remote application 120 as it may appear upon a tablet computer 112 is also shown. As tablet computer and smart phones and even laptop and desktop system continue to enjoy increasing diversities of programming, graphical applications that are not traditional websites are becoming more common A user may have remote application 120, represented by an icon, which when selected instantiates a functional instance of remote application 120 to permit the user to establish, review and/or adjust the irrigation schedule.

More specifically, application 120 is a graphical application that polls the master schedule 206 from the non-volatile memory 204. For at least one embodiment, an initial default master schedule 206 is provided. For at least one embodiment, this default master schedule 206 is defined to be to permit irrigation on each connected irrigation device 118 for a period of 20 minutes starting at what the controller believes to be 6:00 AM. For at least one embodiment, the controller 116 includes instructions to poll, if possible an NTP time server or other network resource to establish the current time for the controller's location of installation.

Indeed it is to be understood and appreciated that in WICS 100, the master schedule 206 for irrigation is maintained by the controller 116. As such, each instance of remote application 120 as may be used to connect to controller 116 is ensured to receive the current schedule. Harmony is thereby also maintained between multiple instances of remote application 120 and/or multiple users.

Moreover, when a computing device 106/112 having remote application 120 loaded thereon is directed to connect to the controller 116, the application will retrieve the master schedule 206 from the non-volatile memory 204 before establishing a change to the schedule and uploading a new master schedule 206 to the non-volatile memory 204. Modification of the master schedule 206 can be handled as an atomic transition to insure that simultaneous, but different schedule adjustments do not occur.

Atomic transactions are guaranteed to have either of two outcomes—either complete execution (commit) or leave no trace of execution (abort), and when multiple processes attempt to perform conflicting atomic transactions simultaneously, their atomic nature guarantees that the transactions that succeed are serializable, meaning that they appear to execute one after the other without intermingling. Guaranteeing atomic transactions frees the programmer from concerns over partial updates occurring, which could lead to corruption of data and/or an errant view of the data. Moreover, to interact attomically is to interact via atomic transactions, such that each interaction either is or is not completely successful.

It should be noted that interactive switch 200C has not been connected. This has been shown so as to demonstrate that controller 116 is able to detect that there are only three current zones, and the application properly reflects them as Zones A, B and C. Moreover, controller 116 permits a user to wire the zones as he or she sees fit, and if a switch is not connected for whatever reason the controller 116 will self adjust.

With respect to the exemplary remote application 120, the master schedule 206 as retrieved from the non-volatile memory 204 is displayed as schedule 220. For at least one embodiment, the user is permitted to turn zones on or off, set start times and duration, and Update the master schedule 206 when he or she is satisfied with the schedule. The application also reports the status of each zone, and as discussed above, Zone A and Zone B corresponding to interactive switches 200A and 200B are shown to be “Good” whereas Zone C corresponding to interactive switch 200D is shown to be “Fault”.

Further still, in this exemplary instance the application 120 indicates that this is an irrigation schedule for “Deb” 222. For the sake of illustration and discussion, this user has been illustrated as authorized to access a controller 116 present in “Deb” 224 and another controller 116 present in “Mike.” The “Mike” 224 button is shown in dotted relief to indicate it is not the current selection.

Moreover, with respect to FIG. 2 WICS 100 can be summarized as having two basic components. The first is a remote scheduler, i.e., the remote application 120 on computer 112, structured and arranged to provide a scheduling interface permitting a user to establish a schedule 220 for at least one interactive zone switch 200 coupled to at least one irrigation device 118.

The second is at least one irrigation controller 116. The irrigation controller 116 including a processor 202, a plurality of interactive zone switches 200 for connection to at least one irrigation device 118, each zone switch further structured and arranged to detect a state of the irrigation device to which it is connected. The controller 116 also includes a non-volatile memory 204, coupled to the processor 202 and having processor executable instructions to direct operation of each interactive zone switch 200. Further, a wireless component 208 is coupled to the processor 202 and the non-volatile memory 204 and is structured and arranged for communication with the remote scheduler to exchange the schedule 206 of at least one interactive zone switch 200.

FIG. 3 illustrates a conceptual circuit 300 layout for at least one prototype embodiment of controller 116. It will be appreciated that circuit 300 does not include a display or key pad input device as is typical with traditional irrigation control systems.

With comparative reference to FIG. 2, in FIG. 3 the memory 204 and processor 202 of FIG. 2 are in FIG. 3 combined as the micro controller 302. The micro controller 302 is coupled to the zone switches 304 as well as a master switch 306, the master switch 306 permitting the micro controller 302 to halt all water flow to the irrigation system in the event that a fault is determined, such as an irrigation device 118 (see FIG. 2) being stuck open, or unintended or excessive water flow detected by water flow sensor 132.

The micro controller 302 is also coupled to the WIFI Module, 308 (wireless network component 208 of FIG. 2), which in turn may be optionally connected to a range extending antenna, 310.

Power from a power supply, such as a wall socket, is received by a power conditioning element 312, which in turn supplies power to the WIFI module 308, the micro controller 302 and the current sensor 314. The current sensor 314, is also coupled to the micro controller 302 and is structured and arranged such that the micro controller 302 is aware of the flow of current indicating that a selected zone switch 304 is properly operating or not.

The micro controller 302 is also coupled to a set of zone indicator LEDs 316, which as suggested above are structured and arranged to indicate the status of each zone—e.g., green for on, red for fault, or light off for off Other colors and or indications may also be provided in varying embodiments.

A reset button 318 is also provided to permit a reset of the controller 116 back to factory default settings. An optional mode button 320 is also provided to permit a user to set the controller 116, and specifically the micro controller 302 into an initializing state for connection via an existing wireless network 118 or ad-hoc wireless connection 114. For the embodiment shown, the micro controller 302 is also coupled to a rain sensor 322 such that if rain is detected, the micro controller 302 will skip scheduled watering.

When the user installs the controller 116 and initializes it, he or she provides the number of zones in his or her watering environment. It is understood and appreciated that in general a user will select a controller 116 with a sufficient number of zone controlling switches to meet the needs of his or her watering environment. For at least one embodiment the controller 116 includes an expansion port, not shown, which permits the connection of an additional set of zone switches to be coupled to the controller—thus permitting the user to advantageously enhance and expand his or her watering environment without requiring a full replacement of the controller 116 component of WICS 100.

FIG. 4, in connection with FIGS. 1 and 2 conceptually illustrates a high level flow diagram depicting at least one method controlling irrigation in accordance with at least one embodiment. It will be appreciated that the described method need not be performed in the order in which it is herein described, but that this description is merely exemplary of one method for controlling irrigation.

In general, the method 400 commences with the controller 116 being provided and installed in a users home or other environment where irrigation system control is desired. More specifically, a plurality of interactive zone switches 200 for connection to at least one irrigation device 118 are provided, block 402. Each interactive zone switch 200 is structured and arranged to detect a state of the irrigation device 118 to which it is connected.

A non-volatile memory 204 coupled to a processor 202 are also provided, the memory having processor executable instructions to direct the operation of each interactive zone switch, block 404. A wireless network component 208 coupled to the processor and non-volatile memory is also provided, block 406. Moreover, blocks 402, 404 and 406 represent the core elements of the controller 116, and as indicated by dotted line 408 are for at least one embodiment pre-fabricated into a single device with a protective housing.

The remote application 120 is also provided to establish via the wireless network component 208 a schedule within the non-volatile memory 204 for operation of each interactive zone switch 200, block 410.

When installed and activated, the controller 116 enters a state of awaiting connection by a user, block 412. Upon the connection by a user, the master schedule is retrieved from memory, block 414. As the controller is not providing web-pages, but merely the data representing the schedule itself, the transfer rate of the master schedule is anticipated to be quite high.

Upon receipt of this data, the remote application 120 interprets the data and provides it to the user graphically for review, block 416. For at least one embodiment the master schedule 206, or metadata transmitted in addition can provide status information regarding the state of each zone. If the user desires to change the schedule, decision 418, he or she manipulates the application to effectuate the desired change and uploads the schedule to the non-volatile memory 204 of the controller 116, block 420. If no change is desired, no action by the user is required.

In at least one embodiment, the controller 116, has a master power switch, so that it can be powered off by a user during desired periods such as winter, or when maintenance is desired. As such, the method 400 permits a decision 422 as to continue or not.

For at least one embodiment, substantially concurrent with the action of waiting for a connection by a user, block 412, the controller 116 also acts to implement the master schedule 206, block 424.

Implementation of the master schedule 206 generally occurs with a scheduled trigger, decision 426. If the schedule does not indicate a scheduled trigger, decision 426, the method 400 may remain in a holding pattern, block 428.

In the event that a trigger is scheduled, decision 424, the method 400 moves to select the triggered irrigation device, or more specifically the interactive switch 200 in control of the irrigation device to be triggered, block 430. The specified irrigation device is then engaged or disengaged in accordance with master schedule 206, block 432.

When the specified irrigation device is activated or deactivated, the method 400 also evaluates the state of the specified irrigation device, block 440. In the event the operation is deemed proper, decision 436, no action is taken. In the event the operation is deemed improper, decision 436, a log entry and or notification to the user is dispatched, block 438.

For at least one optional embodiment, if a schedule does not indicate a scheduled trigger, decision 424, the method 400 may optionally check the state of all connected irrigation devices 118 at periodic intervals, block 438. Where state is determined to be proper, decision 434 no further action is taken. If however, the state is determined to be improper, a log and or notification may be dispatched, block 436. Such proactive monitoring may advantageously help a user of WICS 100 quickly address faults in the irrigation system.

With respect to the exemplary method described, it is clearly understood and appreciated that the schedule may include multiple instances of activation for at least one zone. Moreover, the user may establish a schedule in which zone 1, for example the front lawn, is watered for a total of 30 minutes, but in 5 minute intervals by scheduling 6 different activations. For at least one embodiment, the scheduler may provide the user with the option to automatically divide a scheduled zone activation time period by time intervals or number of activations. In addition, in varying embodiments, the user may establish multiple watering schedules—i.e., front lawn, side lawn and bushes at 6:00 AM every Monday, Wednesday and Friday, and an additional schedule to water the front lawn and vegetables at 4:30 AM on Tuesday and Thursday.

With respect to the above description of WICS 100 and method 400, it is understood and appreciated that the method may be rendered in a variety of different forms of code and instruction as may be preferred for different computer systems and environments. To expand upon the initial suggestion of a processor based device such as computer systems 106/130 and or hand held computer devices 112, such as smart phones or tablet computers shown in FIGS. 1 and 2, and discussed above, FIG. 5 is a high-level block diagram of an exemplary computer system 500. Computer system 500 has a case 502, enclosing a main board 504. The main board has a system bus 506, connection ports 508, a processing unit, such as Central Processing Unit (CPU) 510 and a memory storage device, such as main memory 512, and optionally a solid state drive or hard drive 514 and/or CD/DVD ROM drive 516.

Memory bus 518 couples main memory 512 to CPU 510. In optional configurations the system bus 506 may also couple hard drive 514, CD/DVD ROM drive 516 and connection ports 508 to CPU 510. Multiple input devices may be provided, such as for example a mouse 520 and keyboard 522. Multiple output devices may also be provided, such as for example a video display 524 and a printer (not shown). In varying embodiments, the video display may also be a touch sensitive input device.

Computer system 500 may be a commercially available system, such as a desktop workstation unit provided by IBM, Dell Computers, Gateway, Apple, Sun Micro Systems, or other computer system provider. Computer system 500 may also be a smart phone or tablet computer such as an iPhone or iPad provided by Apple, the HP Slate, the Augen or Archos Android tablets, the Motorola Xoom or other such device.

Computer system 500 may also be a networked computer system, wherein memory storage components such as hard drive 514, additional CPUs 510 and output devices such as printers are provided by physically separate computer systems commonly connected together in the network. Those skilled in the art will understand and appreciate that physical composition of components and component interconnections comprising computer system 500, and select a computer system 500 suitable for use with WICS 100.

When computer system 500 is activated, preferably an operating system 526 will load into main memory 512 as part of the boot strap startup sequence and ready the computer system 500 for operation. At the simplest level, and in the most general sense, the tasks of an operating system fall into specific categories—process management, device management (including application and user interface management) and memory management.

In such a computer system 500, the CPU 510 is operable to perform one or more of the methods of irrigation control as described above. Those skilled in the art will understand that a computer-readable medium 528 on which is the remote application 120 for review, modification and/or establishing the master schedule 206 may be provided to the computer system 500. The form of the medium 528 and language of the program 530 providing the remote application 120 are understood to be appropriate for computer system 500. Utilizing the memory stores, such as for example one or more hard drives 514 and main system memory 512, the operable CPU 502 will read the instructions provided by the computer program 530 and operate to perform the remote application 120 and thereby achieve WICS 100 as described above.

As suggested above with respect to FIG. 1, the computer program 530 may also be provided by a non-portable media such as a disc to a third party computer, such as computer 122, providing an application platform such as but not limited to the Apple App Store. A user can then connect his or her computer 106, or hand held computer 112 to the third party computer, e.g. remote server 122 by a network (wired or wireless) through the Internet 104 other communication channel and obtain remote application 120 so as to adapt his or her computer 106/112/130 to perform the remote application 120 in accordance with WICS 100.

Changes may be made in the above methods, systems and structures without departing from the scope hereof. It should thus be noted that the matter contained in the above description and/or shown in the accompanying drawings should be interpreted as illustrative and not in a limiting sense. The following claims are intended to cover all generic and specific features described herein, as well as all statements of the scope of the present method, system and structure, which, as a matter of language, might be said to fall there between. 

What is claimed is:
 1. A non-transitory machine readable medium on which is stored an application as a computer program for wireless irrigation control, the computer program comprising instructions which when executed by a computer system having at least one processor and a wireless network component performs the steps of: providing a remote scheduler by providing a scheduling interface upon a display of the computer, the scheduling interface permitting a user to establish a schedule for a plurality of interactive zone switches coupled to a plurality of remote irrigation devices, and to directly control each interactive zone switch; connecting to at least one wireless network irrigation controller, comprising: a self containing housing substantially enclosing; a processor; a plurality of independently controllable interactive zone switches for connection to a plurality of remote irrigation devices, each zone switch further structured and arranged to detect a diagnostic state of each irrigation device; a non-volatile memory coupled to the processor having processor executable instructions to direct operation of each interactive zone switch; a wireless network component coupled to the processor and the non-volatile memory.
 2. The non-transitory machine readable medium of claim 1, further including: connecting with the wireless network irrigation controller to retrieve a current schedule from non-volatile memory for display to the user; permitting the user to review the current schedule, and in response to a user directed change to the schedule; changing the schedule in the non-volatile memory.
 3. The non-transitory machine readable medium of claim 1, wherein the application permits the multiple zone activations of each switch per day.
 4. The non-transitory machine readable medium of claim 1, wherein the schedule for at least one zone is automatically divided across multiple activations per day.
 5. The non-transitory machine readable medium of claim 4, wherein the division of the schedule for at least one zone is by time interval.
 6. The non-transitory machine readable medium of claim 1, the non-transitory machine readable medium is provided to a user with the wireless network irrigation controller.
 7. The non-transitory machine readable medium of claim 1, wherein the schedule within the non-volatile memory of the controller is a master schedule, a plurality of remote applications harmoniously adjusting the schedule by retrieving the master schedule from the non-volatile memory before establishing a change to the schedule and uploading a new master schedule to the non-volatile memory.
 8. The non-transitory machine readable medium of claim 1, wherein the application receives notice of the diagnostic state of each irrigation device.
 9. The non-transitory machine readable medium of claim 1, wherein at least one wireless irrigation device is coupled to a water flow sensor, the application receiving notice of unintended or excessive water flow.
 10. A wireless irrigation controller for control by a remote application, comprising: a wireless network irrigation control module having a self containing housing enclosing; a processor; a plurality of independently controllable interactive zone switches for connection to a plurality of remote irrigation devices, each zone switch further structured and arranged to detect a diagnostic state of each irrigation device; a non-volatile memory coupled to the processor having processor executable instructions to direct operation of each interactive zone switch; a wireless network component coupled to the processor and the non-volatile memory, wherein the wireless network controller is adapted for communication with a remote application providing a scheduler to establish a schedule within the non-volatile memory for operation for each interactive zone switch and to receive the schedule from the non-volatile memory in response to a users desire to review or modify the schedule, the application further permitting direct control of each interactive zone switch.
 11. The wireless irrigation controller of claim 10, wherein the remote application is an application in a local area network apart from an Internet.
 12. The wireless irrigation controller of 10, wherein the remote application is provided by a computer in a local area network.
 13. The wireless irrigation controller of 10, wherein the remote application is provided by at least one remote server accessed via an Internet.
 14. The wireless irrigation controller of 10, wherein the remote application is provided by a smart phone, wirelessly communicating with the wireless network irrigation control module.
 15. The wireless irrigation controller of claim 10, wherein the remote application permits the multiple zone activations of each switch per day.
 16. The wireless irrigation controller of 10, wherein the schedule for at least one zone is automatically divided across multiple activations per day.
 17. The wireless irrigation controller of 16, wherein the division of the schedule for at least one zone is by time interval.
 18. The wireless irrigation controller of 10, wherein the schedule within the non-volatile memory of the controller is a master schedule, a plurality of remote applications harmoniously adjusting the schedule by retrieving the master schedule from the non-volatile memory before establishing a change to the schedule and uploading a new master schedule to the non-volatile memory.
 19. The wireless irrigation controller of 10, wherein the wireless network irrigation controller is further coupled to a water flow sensor.
 20. A system for wireless irrigation control with remote application, comprising: a wireless network irrigation control module having a self containing housing enclosing; a processor; a plurality of independently controllable interactive zone switches for connection to a plurality of remote irrigation devices, each zone switch further structured and arranged to detect a diagnostic state of each irrigation device; a non-volatile memory coupled to the processor having processor executable instructions to direct operation of each interactive zone switch; a wireless network component coupled to the processor and the non-volatile memory; at least one remote application to establish a schedule within the non-volatile memory for operation for each interactive zone switch and to receive the schedule from the non-volatile memory in response to a users desire to review or modify the schedule, the application further permitting direct control of each interactive zone switch and providing the user an option to automatically divide the schedule for at least one zone across multiple activations per day.
 21. The system of claim 20, wherein the schedule within the non-volatile memory of the controller is a master schedule, a plurality of remote applications harmoniously adjusting the schedule by retrieving the master schedule from the non-volatile memory before establishing a change to the schedule and uploading a new master schedule to the non-volatile memory.
 22. The system of claim 21, wherein the division of the schedule for at least one zone is by time interval.
 23. The system of claim 21, wherein the division of the schedule for at least one zone is by number of activations.
 24. The system of claim 20, wherein the wireless network irrigation controller is further coupled to a water flow sensor. 